Motivation

Prepare backend connection ID analysis to use the same module graph that backend bundling already sees, without moving connection ID extraction into this PR.

Changes

This PR adds module graph collection to the backend build path used by both production builds and the dev server. During each backend build, the Vite collector observes Rollup moduleParsed events and records app-local, parseable source modules with their transformed ASTs, canonical module IDs, static dependency IDs, and unsupported local dependency facts.

For example, this backend module:

// /app/src/backend/actions.backend.ts
import { getMessage } from "./helpers";

export async function run() {
    return getMessage();
}

Produces a collected module record shaped like this:

{
    id: "/app/src/backend/actions.backend.ts",
    ast: Program,
    staticDependencies: ["/app/src/backend/helpers.ts"],
    unsupportedDependencies: [],
}

The Vite-specific adapter owns Rollup module ID normalization and virtual module filtering, while the backend AST module graph code works with canonical app-local module IDs. That keeps bundler details out of the reusable graph record layer.

This PR intentionally stops at building the graph. Traversing the graph to collect connection IDs from reachable modules is handled in the next PR in the stack. Existing same-file backend connection ID behavior remains unchanged.

QA Instructions

Updated the focused unit coverage for backend module graph record creation and Vite collector behavior. Also ran the apps plugin typecheck and lint coverage for the changed module graph and backend build integration paths.

Validated the change against a local test app to confirm backend functions still build and upload while existing same-file allowedConnectionIds behavior remains unchanged.

Blast Radius

This affects the apps plugin backend build path by collecting module graph metadata during backend builds. The collected graph is not used to change emitted allowedConnectionIds behavior in this PR, so runtime behavior should remain unchanged.

Documentation

• PR Description Guidelines